Collecting Ticket Data

The Emerson ROC800L (809L and 827L) field devices support the retrieval of periodic, batch, and ticket data. Contact Emerson support for information about the applicable firmware versions.

To Collect Ticket Data

1. Using CygNet Explorer, go to the applicable Device Definition Service (DDS) and create a new remote device or open an existing one.
2. If applicable, configure the remote device for basic use, including assigning a communication device and applicable facilities.
3. Click the Data Group page then poll the "ROC Config" (RtuConfig) data group. In the RtuConfig device editor data view, confirm that liquid and transactional history point types (144, 145, 200, 201, 202, 203, 204, and 205) are available on the field device.
4. If you want to pull liquid configuration and value data into the SCADA system for viewing and other purposes, perform these basic steps:
   1. Instantiate the applicable data groups. The following data groups might apply:
      • DensityIF – "Liquid Density Interface"
      • LiqMeter – "Liquid Meter Run Configuration"
      • LiqMtrEx – "Liquid Meters Extended"
      • LiqPref – "Liquid Preferences"
      • LiqProd – "Liquid Products"
      • SPLiq – "Station Parms (Liquids)"
   2. Map UDCs to the applicable data group elements in the data groups.
   3. Create and configure points in the Point Service (PNT) that correspond to the mapped UDCs.
   4. Map the points to an associated application, like CygNet Studio.
   5. If applicable, create commands in applicable services like the DDS, and create polling tasks in the Master Scheduling Service (MSS).
5. If you want to retrieve transactional liquid data that reflects the field device historical database (for example, to create ticket data), perform these basic steps:
   1. Instantiate the following data groups, making sure to carefully associate them with the applicable transaction set for each transaction set you want to poll from your host system, and making sure that each collection of the following data groups shares the same ordinal:
      • TxHist – "Transactional History"
      • Optional: TxHisCfg – "Transactional History Cfg"
      • Optional: TxHisPtCfg – "Transactional History Point Cfg"
      • Optional: TxHisTrig – "Transactional History Trigger"
   2. Poll the TxHist data group.
   3. Map UDCs to the applicable data group elements in the data groups.
   4. Create and configure points in the PNT that correspond to the mapped UDCs.
   5. Map the points to an associated application, like CygNet Studio.
   6. If applicable, create commands in applicable services like the DDS, and create polling tasks in the MSS. You will need to use the TXHISTRG UIS command.
6. If you want to use CygNet Measurement (FMS) to retrieve transactional liquid data that reflects the field device historical database for the purpose of creating tickets, perform these basic steps:
   1. Instantiate the following data group types, making sure to carefully associate them with the applicable FMS ordinal and/or transaction set number:
      • FmsTicket – "FMS Liquid Ticket"
      • FmsProduct – "FMS Liquid Product"
   2. Poll TxHist data groups that share the same ordinal as FmsTicket data groups.
   3. Open applicable FmsTicket data group property sheets one at a time and map process variables to history points. You must specify units. Once configured, the FmsTicket data groups are ready to be polled from the DDS or an associated application, like FMS.
   4. If applicable, create commands in applicable services like the DDS and/or FMS, and create polling tasks in the Master Scheduling Service (MSS). You will need to use the TXHISTRG UIS command.
7. Perform advanced steps to further retrieve and distribute liquid meter data.